Skip to content

Conversation

@dsriseah
Copy link

@dsriseah dsriseah commented Aug 20, 2024

This PR changes the way that npm run dev and npm run package work due to differences in our MacOS shell environment and Digital Ocean's environment.

  1. npm run dev now uses the ./@build-ursys.sh because ./ isn't included in the path by default, as it is in our VSCode integrated terminal
  2. npm run package now also invokes ./@build-ursys.sh because it was not being run at all, causing a potential failure to load in net graphs because the libraries were not built.

See issue #234 for details.

TECHNICAL NOTES

On Digital Ocean running nc-multiplex, the installation instructions call for running npm run package once after doing a pull of the netcreate-itest repo. This is to ensure that all built libraries are available, as nc-multiplex does not do it automatically. Up to now, npm run package did not build the ursys libraries as npm run dev does automatically. This can cause URSYS versions to not be available (showing load errors in the javascript console) or cause URSYS versions to be out-of-date.

NetCreate makes fairly minimum use of URSYS itself with the exception of the "Comments" addon, but the libraries must be present for the app to load.

…d missing @build-ursys to `npm run package`

These are required changes for running with nc-multiplex on digital ocean, where the shell PATH and build requirements dictate this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants